An issue with ufo2fdk is being fixed. see http://code.typesupply.com/changeset/1154 This will be embedded in the next version of RoboFont thanks

this is a formatting bug in the info sheet thanks for spotting it!

its idd not the best solution have to come up with a better and more clever way to handle this issue....

Plausible point of view. (The spec isn't the problem, but it's sometimes problematic to operate in a world where many people are not following the spec (and end-users suffer). In a world where font foundries and application developers are making workarounds for each others workarounds, it's meanwhile impossible to define who is the chicken and who's the egg. Indeed, we're way off topic… :-)

Any plans to make a "Built Names" button in the Font Info panel to quickly build General, Open Type, and Postscript names? This would be a great time saver and much appreciated. I just spent a long time getting my interpolated fonts in a family to show up, finally realizing that I hadn't set the postscript name (this didn't seem to matter so much in fontlab), only having set the general and open type names, and this was causing a conflict with the "unique ID" being the same for multiple fonts.